Improve prefetch & site rendering #253
Open
+1,416
−13,273
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a /browse page showing all publications with client-side pagination, sorting, and card-based layout. Add Browse nav link to header. Convert homepage Browse Articles button from search dialog trigger to /browse link.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
✅ Deploy Preview for insightjournal ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Author
|
@thewtex Can you have a look at this? 👀 After heavy optimization of the IPFS DAG discovery in The meat however is in 97db37d, where I took the liberty of implementing lazy filetree rendering. Now even the chonkiest of publications load quickly :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Main change is to lazily render the filetree on the client, as the existing UI tried to synchronously render DOM elements for every single file in the tree. This broke down terribly for very large publications, e.g. pub 874 with ~12k files in the tree took the backend ~18s to respond, and the subsequent render froze the browser for ~3 minutes.
Only the file tree is lazily rendered on the client, all metadata etc is still SSR so this shouldn't interfere with any indexers.
Misc:
package-lock.jsonNote:
This branch is based on #252